tag:blogger.com,1999:blog-4476863800158400170.post2719816221368638022..comments2022-03-22T15:29:41.873+01:00Eddie Hartmanhttp://www.blogger.com/profile/12264507239868838185noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4476863800158400170.post-44216202463784546222009-10-07T22:11:04.835+02:002009-10-07T22:11:04.835+02:00

These days we are leaning towards using &quot;outside&quot; scheduling: e.g. Windows Scheduler, cronjob, etc. That way even if the TDI Server stops for some reason, you start up a new one with the next invocation. You could even schedule it to run using the tools you know and love in Domino, as long as you can execute a commandline.<br /><br />Or you could set up an AL with the HTTP Server

Eddie Hartmanhttps://www.blogger.com/profile/12264507239868838185noreply@blogger.comtag:blogger.com,1999:blog-4476863800158400170.post-51290579369929708522009-10-07T18:34:56.447+02:002009-10-07T18:34:56.447+02:00

Are there any best practices, war stories about how to put this in place in a medium sized Domino server environment, on Windows? We have a handful of different Notes app servers to get data from. We currently use ZMERGE (Notes API data tool) running via Lotus &quot;Program Document&quot; schedules as well as windows scheduler on 3 servers. On TDI 611 (thanks to the great videos, blogforums and

chuckhttps://www.blogger.com/profile/06294938420998091198noreply@blogger.com